Software Inventory Database                         July 13, 1995   
                                                                                
****************************** TROUBLSH.TXT *****************************
                              (Version 2.1)
--------------------- 
Trouble Shooting Tips 
---------------------

1. SHARE.EXE is required for this program when running Windows 3.1. To 
   see if SHARE is loaded, type the following command at the DOS prompt:
        MEM /C
   Under the Name heading you should see SHARE in the list. If its not
   there you can modify AUTOEXEC.BAT with a line like the following:
        C:\DOS\SHARE.EXE /L:500 /F:5100

2. Check the PATH statement in AUTOEXEC.BAT. Does it include the "correct"
   Windows directory? For example, PATH=C:\;C:\DOS;C:\WINDOWS;
   Also, check for invalid directories in the PATH statement.
   If changes are required, the system must be rebooted before the changes
   will take affect.

3. Is Windows 3.1 or Windows for Workgroups 3.11 running with at least
   DOS 5.0 or greater installed. The program can also be run under
   Windows NT 3.5 as a 16-bit application.

4. The Setup procedure, which installs the program and the application
   program both require VBRUN300.DLL. It should be the in the Windows System
   directory. Disk #2 has a copy of VBRUN300.DLL for users not having
   access to a recent copy. Use the DOS EXPAND command to copy it into the
   Windows\System directory. For example:
         EXPAND A:\VBRUN300.DL_ C:\WINDOWS\SYSTEM\

5. This program needs access to the following modules to run correctly:
   CMDIALOG.VBX, COMMDLG.DLL and THREED.VBX. The installation program
   copies these files to the user-specified diectory when the software is
   installed. To save disk space these files can be deleted from the
   user-specified directory if they already exist in the Windows\System
   directory. Verify that the file dates in the Windows\System are at least
   as current as those in the user-specified directoy.

6. Some files on the install floppies that have a suffix of .DL_, .EX_, etc.,
   are compressed. They can be expanded by using the DOS EXPAND command.
   For example: EXPAND A:\SOFTINVD.EX_ C:\LOCATION

7. When adding other software that use an Access database, certain modules
   may be back-leveled (an older version overlays a newer version). A specific
   example is VBDB300.DLL which can overlay the existing version with the same
   name. The version of VBDB300.DLL that supports Access 2.0 databases has
   a date of 3/24/94. The version that will NOT support Access 2.0 databases
   is dated 4/24/93.
   The error you receive is "cannot find MSAJT110.DLL" when you try to open
   the database.